Thank you for your pull request. Before we can look at it, you'll need to sign a Contributor License Agreement (CLA).

Please follow instructions at https://icinga.com/company/contributor-agreement to sign the CLA.

After that, please reply here with a comment and we'll verify.

Contributors that have not signed yet: @kroseneg

@cla-bot check

Thank you for your pull request. Before we can look at it, you'll need to sign a Contributor License Agreement (CLA).

Please follow instructions at https://icinga.com/company/contributor-agreement to sign the CLA.

After that, please reply here with a comment and we'll verify.

Contributors that have not signed yet: @kroseneg

@cla-bot check

Hi,

I don't think we will merge this for the following reasons:

• It has a massive disadvantage because it only has access to a partial result returned by the database. Only a subset of so called pages will be ordered, though there may be more data on previous/next pages which would influence the shown result.
• Such a functionality won't be added here anymore. Icinga DB Web already supports sorting by multiple columns. The suggestion made here is already possible by using such a sort parameter: ?sort=host.vars.sub1,host.vars.sub0,host.vars.domain
  • A widget in the UI allowing to assemble such a rule more easily is already planned

Though, thanks for your contribution and effort anyway. It just would have been a good idea to ask whether such an implementation is worth taking on 😉